IT Project Management from a Systems Thinking Perspective: A Position Paper

We proposes a Systems Thinking approach to the study of IT project management and show how this approach helps project managers in controlling their projects. To illustrate our proposal, we present an example model of the dynamics of IT out-sourcing projects. The example model explains these dynamics in terms of feedback loops consisting of causal relations re-ported in the literature. The model provides insight in how coordination, trust, information exchange and possibilities for op-portunistic behaviour influence each other and together influence delivery quality, which in turn influences trust. The integra-tion of these insights provided by applying the Systems Thinking perspective helps project managers to reason about how their choices influence project outcome. The Systems Thinking perspective can serve as an additional tool in the academic study of IT project management. Applying the Systems Thinking perspective also calls for additional research in which this perspective is itself the object of study

An Investigation of the Negotiation Domain for Electronic Commerce Information Systems

To support fully automatic business cycles, information systems for electronic commerce need to be able to conduct negotiation automatically. In recent years, a number of general frameworks for automated negotiation have been proposed. Application of such frameworks in a specific negotiation situation entails selecting the proper framework and adapting it to this situation. This selection and adaptation process is driven by the specific characteristics of the situation. This paper presents a systematic investigation of there characteristics and surveys a number of frameworks for automated negotiation

Understanding and Specifying Information Security Needs to Support the Delivery of High Quality Security Services

In this paper we present an approach for specifying and prioritizing information security requirements in organizations. It is important to prioritize security requirements since hundred per cent security is\ud not achievable and the limited resources available should be directed to satisfy the most important ones. We propose to explicitly link security requirements with the organization’s business vision, i.e. to provide business\ud rationale for security requirements. The rationale is then used as a basis for comparing the importance of different security requirements.\ud Furthermore we discuss how to integrate the aforementioned solution concepts into a service level management process for security services, which is an important step in IT Governance. We validate our approach by way of a focus group session

eCustoms Case Study: Mechanisms behind Co-operation Planning

Members of existing e-commerce trading networks constantly assess their network to identify opportunities for increased co-operation and integration of e-commerce IT systems. Failing to identify the mechanisms involved in co-operation compromises correct investment decisions. In this paper, we use Systems Thinking as a reasoning model that helps decision makers to uncover such mechanisms. We use Systems Thinking to analyse a real-world case called eCustoms, an inter-organisational network of customs organisations. The resulting model explains the mechanism of planning co-operation in terms of a feedback loop that comprises political support, operational potential, and information flow. This mechanism also explains why it is important to select potential partners for closer co-operation as early as possible, the importance of willingness to participate, and the gain or loss of decision power that joining a network implies

Discovering Strategies to Improve Business Value in Outsourcing Projects

This paper deals with the problem of leveraging client business value in a software development outsourcing relationship. We have observed software development projects from two different Dutch IT outsourcing companies and studied the approach they apply in their (successful) projects. The results show that they create a role dedicated to facilitate communication. This arrangement has the potential to put team members in a better position to communicate, facilitating the transfer of information supporting the rationale behind design decisions. Teams are thus better equipped to anticipate change and to react faster in solving everyday problems. This paper describes our observations and the practical implications we expect, such as the improvement of re-buy intention on the client's side

A Business Goal Driven Approach for Understanding and Specifying Information Security Requirements

In this paper we present an approach for specifying and prioritizing\ud information security requirements in organizations. It is important\ud to prioritize security requirements since hundred per cent security is\ud not achievable and the limited resources available should be directed to\ud satisfy the most important ones. We propose to link explicitly security\ud requirements with the organization’s business vision, i.e. to provide business\ud rationale for security requirements. The rationale is then used as a\ud basis for comparing the importance of different security requirements.\ud A conceptual framework is presented, where the relationships between\ud business vision, critical impact factors and valuable assets (together with\ud their security requirements) are shown

Correlating Architecture Maturity and Enterprise Systems Usage Maturity to Improve Business/IT Alignment

This paper compares concepts of maturity models in the areas of Enterprise Architecture and Enterprise Systems Usage. We investigate whether these concepts correlate, overlap and explain each other. The two maturity models are applied in a case study. We conclude that although it is possible to fully relate constructs from both kinds of models, having a mature architecture function in a company does not imply a high Enterprise Systems Usage maturity

Architecture alignment in a large government organization : a case study

In this paper we view IT architecture as the structures present in the entire information technology support used by an organization. Research into IT architecture either is of a strategic nature, yielding no operational guidelines for the practicing IT-architect, or it is part of software engineering, yielding no guidelines that related software architecture to the business environment. In this paper we report on a detailed case study of an operational IT architecture process, in which we investigated the relationship between IT architecture and business context. We analyze this process in terms of a conceptual framework for IT architecture presented earlier. The major findings are that in this case study there is a close relationship between IT architecture and the structure of the IT department, which makes IT architecture design also a problem of organizational design; that application architecture is designed by aligning applications to the business process structure; and that IT infrastructure architecture is designed by aligning it to technological trends rather than to business goals and problems. This paper reports about a single case study done in a series of case studies. We discuss the generalizability of the findings from this case study, and discuss topics for further research

Validating adequacy and suitability of business-IT alignment criteria in an inter-enterprise maturity model

Aligning requirements of a business with its information technology is currently a major issue in enterprise computing. Existing literature indicates important criteria to judge the level of alignment between business and IT within a single enterprise. However, identifying such criteria in an inter-enterprise setting – or re-thinking the existing ones – is hardly addressed at all. Business-IT alignment in such settings poses new challenges, as in inter-enterprise collaborations, alignment is driven by economic processes instead of centralized decision-making processes. In our research, we develop a maturity model for business-IT alignment in inter-enterprise settings that takes this difference into account. In this paper, we report on a multi-method approach we devised to confront the validation of the business-IT alignment criteria that we included in the maturity model. As independent feedback is critical for our validation, we used a focus group session and a case study as instruments to take the first step in validating the business-IT alignment criteria. We present how we applied our approach, what we learnt, and what the implications were for our model

Developing an inter-enterprise alignment maturity model: research challenges and solutions

Business-IT alignment is pervasive today, as organizations strive to achieve competitive advantage. Like in other areas, e.g., software development, maintenance and IT services, there are maturity models to assess such alignment. Those models, however, do not specifically address the aspects needed for achieving alignment between business and IT in inter-enterprise settings. In this paper, we present the challenges we face in the development of an inter-enterprise alignment maturity model, as well as the current solutions to counter these problems